@EresDev https://github.com/ubiquity/pay.ubq.fi/actions/runs/9567051444/attempts/1

It seems the project was uploaded to cloudflare but the CI failed on posting a comment in a PR because of reaching API limit. It makes sense to wait for some time and try again later.

Doesn't look right, unless you re-ran manually!

c124c0a
c124c0a
c124c0a
c124c0a

@EresDev Now we need to merge the latest development to the beta branch so that a new project beta-pay-ubq-fi is created in cloudflare dashboard, right?

Doesn't look right, unless you re-ran manually!

c124c0a
c124c0a
c124c0a
c124c0a

I am unable to see what is wrong in these links. If you are expecting to see gift card on the above URL, the commit belongs to development branch and development branch doesn't have gift cards yet.

Or, you are probably referring to API limit, then yes re-running it manually worked.

@EresDev Now we need to merge the latest development to the beta branch so that a new project beta-pay-ubq-fi is created in cloudflare dashboard, right?

beta branch has already what we have added a few hours ago to development for deployment. No need to merge.
The cloudflare deploy action creates a new project by repository name, not branch name. Cloudflare will only create a new project if there is not an existing project with given repository name. Because there is already a project pay.ubq.fi on cloudflare, it will not create a new project, and will just use the existing one.
I didn't change anything related to the creation of new project in the deploy workflow. The process is the same as it was before the gift card.

If the "deploy to cloudflare" workflow was successful, you can see in its logs if a new project was created in the cloudflare or an existing one was used.

Currently asking @Steveantor to delete their usage of the namespace.

Otherwise we are currently using pay-ubq-fi-bxp.pages.dev